docs: update license year range to 2024#5890
Conversation
knst
changed the title
knst
changed the title
|
Removed "backport candidate" as that is (currently) for v20.0.5 theoretically; not v20.1; develop is still v20.1 |
I added a label for possible v20.0.5 if any between release would be done |
hmmm yeah; but I don't think this is worth backporting even if we do need v20.0.5, unless you want to do a new PR that runs the copyright bump instead of in this PR |
PastaPastaPasta
left a comment
PastaPastaPasta
left a comment
There was a problem hiding this comment.
utACK for squash merge
A notice for next year: copyright year for sources should be bumped at the end of year next time; license year is preferred to bump after NY |
796a844 doc: Update license year range to 2026 (Konstantin Akimov) Pull request description: ## What was done? Annual copyright bump. Prior PRs: #5890, #6546 ## How Has This Been Tested? N/A ## Breaking Changes N/A ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_ ACKs for top commit: UdjinM6: utACK 796a844 (should probably be `chore`, not `doc`) kwvg: utACK 796a844 Tree-SHA512: fd3406a7261f16b24c1d16b05591358dc7ed4d54e238b4a1f8d5cd3ab30888c84565361334774b7eaee0c3ae60d34d468e778ec29bf66cabe86dcf26ed341afc
3 participants
What was done?
Happy new year and happy new lunar year!
2024 is here and 20.1 is coming.
Breaking Changes
N/A
Checklist: